Vehicle management and mission management computer architecture and packaging

ABSTRACT

A vehicle management and mission management computer architecture and packaging may include a first line replaceable unit and a second line replaceable unit. The first line replaceable unit may include a vehicle management system computer channel coupleable to a group including at least one mission related system and at least one vehicle system. The first line replaceable unit may also include a mission management system computer channel coupleable to the group including the at least one mission related system and the at least one vehicle system. The second line replaceable unit may include another vehicle management system computer channel coupleable to the group including the at least one mission related system and the at least one vehicle system. The second line replaceable unit may also include another mission management system computer channel coupleable to the group including the at least one mission related system and the at least one vehicle system.

CROSS-REFERENCE TO RELATED APPLICATIONS

This application is a divisional of U.S. patent application Ser. No.11/534,461 filed on Sep. 22, 2006, the disclosure of which is herebyincorporated by reference herein for all purposes.

BACKGROUND OF THE INVENTION

The present invention relates to computer architecture and packaging andmore particularly to a vehicle management and mission managementcomputer architecture and packaging for unmanned vehicles or the like.

Vehicles, such as unmanned vehicles or the like, typically have systemsrelated to the operation of the vehicle and systems related to themission of the vehicle. Examples of vehicle related systems may includevehicle propulsion systems, fuel systems, electrical systems, hydraulicsystems, flight termination systems and the like. Examples of missionrelated systems may include communications systems, intelligence,surveillance and reconnaissance (ISR) systems, weapons systems and thelike. Each of these systems may be controlled by management systemcomputers or the like. In some applications, particularly those that mayrequire high altitude and long endurance, low weight and reliablevehicle management system (VMS) and mission management system (MMS)computing are needed to meet the long endurance and high missionreliability goals.

BRIEF SUMMARY OF THE INVENTION

In accordance with an embodiment of the present invention, a vehiclemanagement and mission management computer architecture and packagingmay include a first line replaceable unit and a second line replaceableunit. The first line replaceable unit may include a vehicle managementsystem computer channel coupleable to a group including at least onemission related system and at least one vehicle system. The first linereplaceable unit may also include a mission management system computerchannel coupleable to the group including the at least one missionrelated system and the at least one vehicle system. The second linereplaceable unit may include another vehicle management system computerchannel coupleable to the group including the at least one missionrelated system and the at least one vehicle system, and the second linereplaceable unit may also include another mission management systemcomputer channel coupleable to the group including the at least onemission related system and the at least one vehicle system.

In accordance with another embodiment of the present invention, avehicle management and mission management computer architecture andpackaging may include a first line replaceable unit and a second linereplaceable unit. A pair of vehicle management system computer channelsmay be included in each line replaceable unit, and a pair of missionmanagement system computer channels may also be included in each linereplaceable unit.

In accordance with another embodiment of the present invention, avehicle may include at least one vehicle system and at least one missionrelated system. The vehicle may also include a vehicle management andmission management computer architecture and packaging. The vehiclemanagement and mission management computer architecture and packagingmay include a first line replaceable unit and a second line replaceableunit. The first line replaceable unit may include a vehicle managementsystem computer channel coupled to the at least one mission relatedsystem and the at least one vehicle system. The first line replaceableunit may also include a mission management system computer channelcoupled to the at least one mission related system and the at least onevehicle system. The second line replaceable unit may include anothervehicle management system computer channel coupled to the at least onemission related system and the at least one vehicle system. The secondline replaceable unit may also include another mission management systemcomputer channel coupled to the at least one mission related system andthe at least one vehicle system.

In accordance with another embodiment of the present invention, a methodto provide vehicle management and mission management in a low weight andreliable architecture may include providing a first line replaceableunit and a second line replaceable unit. The method may also includeproviding at least one vehicle management system computer channel ineach line replaceable unit; and at least one mission management systemcomputer channel in each line replaceable unit.

Other aspects and features of the present invention, as defined solelyby the claims, will become apparent to those ordinarily skilled in theart upon review of the following non-limited detailed description of theinvention in conjunction with the accompanying figures.

BRIEF DESCRIPTION OF THE SEVERAL VIEWS OF THE DRAWINGS

FIGS. 1A and 1B (collectively FIG. 1) are a block diagram of an exampleof a vehicle management system computer and mission management systemcomputer architecture and packaging in accordance with an embodiment ofthe present invention.

FIG. 2 is a block diagram of an example of a line replaceable unit (LRU)in accordance with an embodiment of the present invention.

FIG. 3 is an illustration of an example of a vehicle including a vehiclemanagement computer system and mission management computer systemarchitecture and packaging in accordance with an embodiment of thepresent invention.

DETAILED DESCRIPTION OF THE INVENTION

The following detailed description of embodiments refers to theaccompanying drawings, which illustrate specific embodiments of theinvention. Other embodiments having different structures and operationsdo not depart from the scope of the present invention.

FIGS. 1A and 1B (collectively FIG. 1) are a block diagram of an exampleof a vehicle management system computer (VMSC) and mission managementsystem computer (MMSC) architecture and packaging 100 in accordance withan embodiment of the present invention. The VMSC and MMSC architectureand packaging 100 may include a first line replaceable unit 102 a and asecond line replaceable unit 102 b. Each line replaceable unit 102 mayinclude two VMSCs or VMSC channels 104 and two MMSCs or MMSC channels106. In the embodiment illustrated in FIGS. 1A and 1B, the first linereplaceable unit 102 a may include VMSC Channel #1 104 a, VMSC channel#2 104 b, MMSC Channel #1 106 a (FIG. 1B) and MMSC Channel #2 106 b(FIG. 1B). The second line replaceable unit 102 b may include VMSCChannel #3 104 c, VMSC Channel #4 104 d, MMSC Channel #3 106 c (FIG. 1B)and MMSC Channel #4 106 d (FIG. 1B). The line replaceable units 102 aand 102 b may be identical.

FIGS. 1A and 1B each illustrate examples of the same line replaceableunits 102 a and 102 b. For purposes of clarity and explanation, FIG. 1Aillustrates the VMSC channels 104 and an associated VMSC busarchitecture 108, and FIG. 1B illustrates the MMSC channels 106 and anassociated MMSC bus architecture 110. The MMSC channels 106 areillustrated in phantom or broken lines in FIG. 1A. Similarly, the VMSCchannels 104 are illustrated in phantom or broken lines in FIG. 1B.

The vehicle management and mission management computer architecture andpackaging 100 may include a VMSC common bus 112 (FIG. 1A) couplingtogether the VMSC channels 104 and the MMSC channels 106. The VMSCcommon bus 112 may be further adapted to couple the channels 104 and 106to one or more mission related systems 114. Mission related systems 114may include mission communications hardware 117 or equipment and missionpayload 118 or other equipment or systems needed to perform a particularmission or purpose. Examples of mission communications hardware 117 mayinclude radios or other communications devices. Examples of missionpayload 118 may include intelligence, surveillance and reconnaissance(ISR) equipment or systems, weapons systems, or other systems to performa predefined mission.

The vehicle management and mission management computer architecture andpackaging 100 may also include a MMSC common bus 116 (FIG. 1B) to coupletogether the MMSC channels 106 and the VMSC channels 104. The VMSCcommon bus 112 and the MMSC common bus 116 may be a single common bus.The MMSC common bus 116 may be further adapted to couple the channels104 and 106 to one or more vehicle systems 120. Vehicle systems 120 maybe those systems necessary to operate the vehicle to perform thepredefined mission. Examples of vehicle systems 120 may includepropulsion systems, fuel systems, air data, electrical systems, flighttermination systems and other systems needed for operation of thevehicle.

The VMSC bus architecture 108 (FIG. 1A) may also include a separategroup of VMSC buses 122. Each separate VMSC bus 122 may couple arespective one of the VMSC channels 104 to one or more vehicle systems120.

Similarly, the MMSC bus architecture 110 (FIG. 1B) may include aseparate group of MMSC buses 124. Each separate MMSC bus 124 may couplea respective one of the MMSC channels 106 to one or more mission relatedsystems 114.

The VMSC and MMSC architecture and packaging 100 may also include achannel restart feature 126. A cross channel data link architecture 128may be provided to exchange data between channels and to supportredundancy management voting and the channel restart feature 126 orcapability. A channel restart capability may be provided in the eventthat a VMSC channel 104 or a MMSC channel 106 becomes corrupted duringoperation. A possible cause of corruption may be a single event upset(SEU) where a gamma ray corrupts a memory component within a channel. Toaccomplish channel restart, the effected channel must reboot and itsstates must be reinitialized from correctly operating channels using thecross channel data links 128.

In accordance with one embodiment of the present invention illustratedin FIGS. 1A and 1B, the cross channel data link architecture 128 mayinclude a plurality of cross channel data links 130, at least onebetween each VMSC channel 104 in the first and second LRUs 102 andanother plurality of cross channel data links 132, at least one betweeneach MMSC channel 106 in the first and second LRUs 102.

The VMSC and MMSC architecture and packaging 100 may also include a VMSCEthernet 142 (FIG. 1A) to couple the VMSC channels 104 and the MMSCchannels 106 and may further couple the channels to one or more missionrelated systems 114.

Similarly, the VMSC and MMSC architecture and packaging 100 may includea MMSC Ethernet 144 (FIG. 1B) to couple the VMSC channels 104 and MMSCchannels 106 and may further couple the channels to at least one vehiclesystem 120. The VMSC Ethernet 142 and MMSC Ethernet 144 may be a singlesystem.

The VMSC channels 104 may also be coupled to one or more actuators 146,flight control systems or similar apparatus associated with a vehiclewhere the VMSC/MMSC architecture and packaging 100 may be deployed. TheVMSC channels 104 may be coupled to the actuator or actuators bysuitable links and/or connectors 148. The actuators 146 may be flightcontrol actuators to control flight control surfaces, utility actuators,such as landing gear, doors or components. The links 148 may be digitallinks or connections.

As will be described in more detail with reference to FIG. 2, each ofthe VMSC channels 104 may include a global positioning system (GPS)receiver. Accordingly, each of the VMSC channels 104 may be coupled to aGPS antenna 150 by a suitable connection 152.

The VMSC and MMSC architecture and packaging 100 may further include abus 154 associated with each MMSC Channel 106 for MMS growth 156.Examples of the MMS growth 156 may include other mission relatedequipment or operations.

FIG. 2 is a block diagram of an example of a line replaceable unit (LRU)200 in accordance with an embodiment of the present invention. The LRU200 may be used for each of the line replaceable units 102 a and 102 bin FIGS. 1A and 1B. The LRU 200 may include a pair of vehicle managementsystem computer (VMSC) channels 202 a and 202 b and a pair of missionmanagement system computer (MMSC) channels 204 a and 204 b. The primaryfunction of the VMSC channels 202 may be to monitor and command orcontrol vehicle subsystems as may be required for autonomous operationor other operation. For example, in unmanned aerospace vehicles, theVMSC channels 202 may monitor and control vehicle subsystems toautonomously operate the vehicle during ground operations (i.e. takeoffand landing) and airborne or flight operations (i.e. fly a particularcourse or route, fly at particular altitudes, etc.). The MMSC channels204 may monitor and command or control communications systems, ISRsystems, aerial spraying systems, weapons systems or other missionrelated systems as needed to achieve mission goals.

Each VMSC channel 202 may include a processor 206 or processor core tocontrol overall operation of the VMSC channel 202 and the othercomponents. The processor 206 may access a memory 208 or storage devicefor storing programs or applications that may operate or run on theprocessor 206 for particular vehicle operations. Each VMSC channel 202may also include a global positioning system (GPS) receiver 210 and aninertial measurement unit (IMU) 212. The GPS receiver 210 may be used todetermine a geographic location of the vehicle on which the LRU 200 isoperating and to assist with guidance or navigation of the vehicle. TheIMU 212 may provide measurements of vehicle movement, such as vehiclerotation rates, linear accelerations and the like for flight controlsand navigation algorithms. The IMU 212 may be a Honeywell HG1700 asmanufactured by Honeywell, Minneapolis, Minn., or a similar device. Forairborne applications, each VMSC channel 202 may also include a radaraltimeter to provide altitude measurements for control and guidance ofthe vehicle.

The VMSC channel 202 may also include a power supply 216 to power thevarious components of the VMSC channel 202 that may require power. Dataconnections 218 between the different components of the VMSC channel areillustrated by a dashed or broken line in FIG. 2 and power distributionlines 220 are illustrated by solid lines in FIG. 2. The VMSC channel 202may also include one or more bus connections or connectors 222 to couplethe VMSC channel 202 to various vehicle systems and mission relatedsystems, such as vehicle systems 120 and mission related systems 114,similar to that described with respect to FIGS. 1A and 1B.

Each MMSC channel 204 may include a processor 224 or processor core anda memory 226 that may store programs or applications operable on theprocessor 224 as well as other data. The processor 224 and memory 226may be the same as processor 206 and memory 208 of the VMSC channels202. A power supply 228 may also be included to provide power foroperation of the processor 224 and any other components of the MMSCchannel 204 that may require power. The MMSC channel 204 may alsoinclude bus connectors 230 or connections to couple the MMSC channel 204to the various mission related systems and vehicle systems similar tothe architectures described in FIGS. 1A and 1B.

The computing channels 202 and 204 may be electrically independent,particularly between LRUs to protect the system from potential faultsthat could take down or render inoperative all computing channels in agiven LRU. However, all channels 202 and 204 within an LRU 200 may sharea common ground 232.

FIG. 3 is an illustration of an example of a vehicle 300 including amultiple redundant system 302 or vehicle management computer system andmission management computer system architecture and packaging inaccordance with an embodiment of the present invention. The vehicle 300illustrated in FIG. 3 may be an aerospace vehicle, such as an unmannedaircraft or the like, but the present invention may also be applicableto water craft and terrestrial vehicles which may be manned or unmanned.The vehicle management and mission management computer architecture andpackaging 300 may provide quad redundant VMS and MMS computing using twoline replaceable units (LRUs) 304 a and 304 b. The LRUs 304 may besimilar to the LRU 200 described with reference to FIG. 2 and the VMSand MMS computer architecture and packaging 302 may be similar to thatdescribed with reference to FIGS. 1A and 1B.

The two LRUs 304 a and 304 b may be identical and may each include twoVMS computing channels 306 and two MMS computing channels 308. Placingmultiple computing channels 306 and 308 in each LRU 304 reduces weightof the overall package 302. Separating the quad redundant VMS 306 andMMS 308 computing into 2 channels per LRU 304 protects the system frompotential faults that could take down or render inoperative allcomputing channels in a given LRU 304. Even though multiple channels 306and 308 are included in a given LRU 304, all computing channels 306 and308 may be electrically independent with the exception of channelswithin a given LRU 304 sharing a common ground plane, similar to thatdescribed with reference to FIG. 2.

The VMS 306 and MMS 308 computing channels may use common processor andmemory hardware elements similar to FIG. 2. The primary differencebetween VMS and MMS hardware may be that the VMSC channels 306 mayinclude unique sensors or components. As previously described withreference to FIG. 2, the VMS 306 unique sensors or components mayinclude an inertial measurement unit (quad) (212 in FIG. 2), globalpositioning system receiver (quad) (210 in FIG. 2), and radar altimeter(dual) (214 in FIG. 2). Similar to that described with respect to FIGS.1A and 1B, the VMS channels 306 and the MMS channels 308 may includecross channel data links that exchange data between channels to supportredundancy management voting and channel restart capability.

Desirable characteristics of the present invention include light weightand high reliability providing benefit to long endurance applications.Since long endurance is important to unmanned aircraft applications, thepresent invention has applicability to such technology.

The flowcharts and block diagrams in the Figures illustrate thearchitecture, functionality, and operation of possible implementationsof systems, methods and computer program products according to variousembodiments of the present invention. In this regard, each block in theflowchart or block diagrams may represent a module, segment, or portionof code, which comprises one or more executable instructions forimplementing the specified logical function(s). It should also be notedthat, in some alternative implementations, the functions noted in theblock may occur out of the order noted in the figures. For example, twoblocks shown in succession may, in fact, be executed substantiallyconcurrently, or the blocks may sometimes be executed in the reverseorder, depending upon the functionality involved. It will also be notedthat each block of the block diagrams and/or flowchart illustration, andcombinations of blocks in the block diagrams and/or flowchartillustration, can be implemented by special purpose hardware-basedsystems which perform the specified functions or acts, or combinationsof special purpose hardware and computer instructions.

The terminology used herein is for the purpose of describing particularembodiments only and is not intended to be limiting of the invention. Asused herein, the singular forms “a”, “an” and “the” are intended toinclude the plural forms as well, unless the context clearly indicatesotherwise. It will be further understood that the terms “comprises”and/or “comprising,” when used in this specification, specify thepresence of stated features, integers, steps, operations, elements,and/or components, but do not preclude the presence or addition of oneor more other features, integers, steps, operations, elements,components, and/or groups thereof.

Although specific embodiments have been illustrated and describedherein, those of ordinary skill in the art appreciate that anyarrangement which is calculated to achieve the same purpose may besubstituted for the specific embodiments shown and that the inventionhas other applications in other environments. This application isintended to cover any adaptations or variations of the presentinvention. The following claims are in no way intended to limit thescope of the invention to the specific embodiments described herein.

1-17. (canceled)
 18. A vehicle management and mission managementcomputer architecture and packaging, comprising: a first linereplaceable unit; a second line replaceable unit; a pair of vehiclemanagement system computer channels in each line replaceable unit; and apair of mission management system computer channels in each linereplaceable unit.
 19. The vehicle management and mission managementcomputer architecture and packaging of claim 1, further comprising: acommon bus coupling together each vehicle management system computerchannel and each mission management system computer channel, and whereinthe common bus is adapted to couple each of the channels to at least onemission related system; and a separate bus to couple each of the vehiclemanagement system computer channels to at least one vehicle system. 20.The vehicle management and mission management computer architecture andpackaging of claim 18, further comprising: a common bus couplingtogether each vehicle management system computer channel and eachmission management system computer channel, and wherein the common busis adapted to couple each of the channels to at least one vehiclesystem; and a separate bus to couple each of the mission managementsystem computer channels to at least one mission related system.
 21. Thevehicle management and mission management computer architecture andpackaging of claim 18, further comprising a channel restart feature. 22.The vehicle management and mission management computer architecture andpackaging of claim 18, further comprising a cross channel data linkarchitecture to exchange data between channels and to support redundancymanagement voting and channel restart capability.
 23. The vehiclemanagement and mission management computer architecture and packaging ofclaim 22, wherein the cross channel data link architecture comprises: aplurality of cross channel data links to couple each of the vehiclemanagement system computing channels in the first and second linereplaceable units; and another plurality of cross channel data links tocouple each of the mission management system computing channels in thefirst and line replaceable units.
 24. The vehicle management and missionmanagement computer architecture and packaging of claim 18, furthercomprising fault protection to prevent all channels in a linereplaceable unit from going down. 25-32. (canceled)
 33. A method toprovide vehicle management and mission management in a low weight andreliable architecture, comprising: providing a first line replaceableunit; providing a second line replaceable unit; providing at least onevehicle management system computer channel in each line replaceableunit; and providing at least one mission management system computerchannel in each line replaceable unit.
 34. The method of claim 33,further comprising: coupling together each vehicle management systemcomputer channel and each mission management system computer channelwith a common bus; adapting the common bus to couple each of thechannels to at least one mission related system; and coupling each ofthe vehicle management system computer channels to at least one vehiclesystem by a separate bus.
 35. The method of claim 33, furthercomprising: coupling together each mission management system computerchannel and each vehicle management system computer channel with acommon bus; adapting the common bus to couple each of the channels to atleast one vehicle system; and coupling each of the mission managementsystem computer channels to at least one mission related system by aseparate bus.
 36. The method of claim 33, further comprising providing achannel restart feature.
 37. The method of claim 33, further comprising:coupling a plurality of cross channel data links between each of thevehicle management system computer channels in the first and second linereplaceable units; and coupling another plurality of cross channel datalinks between each of the mission management system computer channels inthe first and second line replaceable units.
 38. The method of claim 33,wherein each channel is electrically independent.
 39. The method ofclaim 38, further comprising separating a quad redundant vehiclemanagement system computing architecture and a mission management systemcomputing architecture into two channels each per line replaceable unit.40. A vehicle management and mission management computer architectureand packaging, comprising: a plurality of VMSC channels forcommunications with a plurality of vehicle systems, each vehicle systembeing related to operation of a vehicle; a plurality of MMSC channelsfor communications with a plurality of mission systems, each missionsystem being related to a mission performable by the vehicle; a VMSCcommon bus coupling together each of the plurality of VMSC channels andadapted to couple each of the plurality of VMSC channels to each missionsystem; a separate VMSC bus to couple each VMSC channel to each vehiclesystem; a MMSC common bus coupling together each of the plurality ofMMSC channels and adapted to couple each of the plurality of MMSCchannels to each vehicles system; and a separate MMSC bus to couple eachMMSC channel to each mission system.
 41. The vehicle management andmission management computer architecture and packaging of claim 40,further comprising a cross channel data link architecture to exchangedata between channels and to support redundancy management voting andchannel restart capability.
 42. The vehicle management and missionmanagement computer architecture and packaging of claim 41, wherein thecross channel data link architecture comprises: a plurality of crosschannel data links to couple each of the VMSC channels; and anotherplurality of cross channel data links to couple each of the MMSCchannels.
 43. The vehicle management and mission management computerarchitecture and packaging of claim 40, further comprising a faultprotection feature to prevent all VMSC channels and MMSC channels in asingle line replaceable unit from becoming inoperative.
 44. The vehiclemanagement and mission management computer architecture and packaging ofclaim 43, wherein the fault protection feature comprises a quadredundant VMSC architecture and MMSC architecture separated into twochannels per line replaceable unit.
 45. The vehicle management andmission management computer architecture and packaging of claim 40,wherein vehicle comprises one of an aerospace vehicle, a watercraft, anda terrestrial vehicle.